Skip to content

feat: TaskKey to propagate name#1537

Open
octonato wants to merge 1 commit intomulti-agent-devfrom
octonato/logging-task-name
Open

feat: TaskKey to propagate name#1537
octonato wants to merge 1 commit intomulti-agent-devfrom
octonato/logging-task-name

Conversation

@octonato
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions bot added the documentation documentation related label Apr 16, 2026
@octonato octonato force-pushed the octonato/logging-task-name branch from 3c96483 to eba915c Compare April 16, 2026 18:16
*/
default void assignTasks(String... taskIds) {
assignTasksAsync(taskIds).toCompletableFuture().join();
default void assignTasks(TaskKey... taskKeys) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requiring the key in client api? Is this going in the right direction?
I didn't notice when reviewing the runtime PR.

}

override def assignTasksAsync(taskIds: String*): CompletionStage[Done] = {
override def assignTasksAsync(taskKeys: TaskKey*): CompletionStage[Done] = {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be easier to keep task ids in the client api? For example, it's more difficult to pass around a composite key in http request/responses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation documentation related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants